home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Mega Doom 1
/
Mega Doom 1.iso
/
utils
/
tcpset9b
/
tcpsetup.doc
next >
Wrap
Text File
|
1994-04-07
|
6KB
|
139 lines
DOOM TCP/IP Network Driver, version 0.9Beta
by Jake Page
(with the use of ipxsetup source generously supplied by id Software,
and the WATTCP library by Erick Engelke and others)
** NOTE: this version is NOT compatible with any earlier release.
New to this version:
* the major change involves 3 & 4 player games. I have added a few
hacks that will _hopefully_ help things. id has said that they will
make changes to their net startup in their next release that should
fix the problem for good (for IPX games as well).
* user can specify port number for connection. I have changed the
default port to 5029, since several people said it made their lives
difficult when messing around with UNIX stuff (which reserves ports
< 1024). 5029 is used because this is the same port the NeXT version
of DOOM uses (though I don't think the packets are compatible-- yet.)
However, there is also an option, "-port <portnumber>" to select
the port. All players in a game MUST use the same port to play.
Version 0.8 used 666 (I HAD to do it...), but version 0.8 is NOT
compatible with 0.9.
* I rewrote/modified several of the library routines that I was using,
dropping the size of the executable to about 37k, and hopefully
improving performance as well (though not much can be done to help
speed up those LONG distance games...)
This uses a standard packet driver to access the ethernet card, so
if you don't have one, you'll have to find one for your card.
I am using the Crynwr driver with a 3c503, and it works fine.
if you need a packet driver, a collection for most cards (with
instructions) can be found by anonymous ftp at
wuarchive.wustl.edu in /systems/ibmpc/msdos/pktdrvr/pktd11.zip,
(or at any SIMTEL20 mirror in */pktdrvr/pktd11.zip).
You must set the information in the WATTCP.CFG to your particular
setup (IP, gateway, nameserver, etc.)
Parameters to pass to TCPSETUP are as follows:
TCPSETUP [other game parameters] -net <node#> [host2 host3 host4]
where <node#> is a number between 1 and 4. It determines who "calls"
who to set up the socket connections, and will also be the player number
in the game. host2-host4 are the other computers in the game, which
can be specified as either a host name or an IP address. Their order
MUST be consistent across all players in the game, from 1-4 with
the local host excluded.
Example 4 player game setup:
player1> tcpsetup -net 1 player2 player3 player4
player2> tcpsetup -net 2 player1 player3 player4
player3> tcpsetup -net 3 player1 player2 player4
player4> tcpsetup -net 4 player1 player2 player3
(If you have seen the NeXT version, you might have noticed that this
basically follows that format...)
The program determines the number of players by these hosts as well as the
node number. So, for example, if you are player 1, any hosts after the
node number will add to the total player count. This means that you should
NOT specify, say, "-net 4" with only two other hosts. I know, it's not the
best way to do it, but right now I'm still concerned with the thing working
at all...
Since my parameter parsing is only semi-intelligent, it's important that
the "-net" parameter is LAST. So if you want to set deathmode, skill,
mission, etc, you have to put them BEFORE -net, or the setup will think
that they are host names.
Other parameters:
-vector 0x??
where ?? is a number between 60-66. This sets the interrupt
vector DOOM will use, rather than searching for a free one.
Not recommended-- you MUST make sure the packet driver isn't
already using this vector.
-port <portnumber>
allows you to specify a port number, instead of using the default
5029. Version 0.8 used 666, but this can sometimes be reserved.
******************
FREQUENT PROBLEMS:
******************
NOTE: at most times when the setup is "stuck" looking for other nodes,
etc, pressing ESC (or alternatively Ctrl-Break) should exit.
* Get "NO PACKET DRIVER FOUND" when running tcpsetup:
- make sure that you have a packet driver correctly loaded,
and there is no other net software loaded (you might be able
to use PKTMUX to do this, but I haven't tried).
- if you need a packet driver, a collection for most cards (with
instructions) can be found by anonymous ftp at
wuarchive.wustl.edu in /systems/ibmpc/msdos/pktdrvr/pktd11.zip,
(or at any SIMTEL20 mirror in */pktdrvr/pktd11.zip).
* Hangs at "listening for node..." in tcpsetup.
- as above, make sure there are no other programs using the packet
driver.
- make sure that the WATTCP.CFG file is in the same directory as
tcpsetup, and is corretly configured.
- make sure that the command line parameters are correct; with a
2 player game, one player uses "-net 1 <addr2>", the other
"-net 2 <addr1>"-- the number does NOT specify the number of players
in the game.
* Hangs at "sending(listening for) network start info...".
- this is in the DOOM setup, so I really don't know.
* In a 3 or 4 player game, gets into DOOM and doesn't crash (player 1
usually sees graphics, all players can use menus, but there is no
action).
- this is a common problem seen for 3 & 4 player games. It is
(probably) due to DOOM's network startup sending too many packets
and thus overloading the other nodes. I have tried to limit the
number of packets sent in startup, but I don't guarantee anything.
The best fix will be when id releases DOOM 1.3.
Feel free to report any problems, suggestions, etc. (or offers to "test"
it, of course...) to me at:
snake@leland.stanford.edu
Jake Page
4/07/94